Conversation
TODO: remove from stats files
Thank you!Thank you for your pull request 😃 🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}. If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
Rendered Changes🔍 Inspect the changes: https://github.com/ResearchCodingClub/python-testing-for-research/compare/md-outputs..md-outputs-PR-12 The following changes were observed in the rendered markdown documents: What does this mean?If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation. ⏱️ Updated at 2026-02-16 15:39:34 +0000 |
Co-authored-by: Ava <avadean7@hotmail.com>
Co-authored-by: Ava <avadean7@hotmail.com>
Co-authored-by: Ava <avadean7@hotmail.com>
|
Thanks for the comments @avadean! Ironically I hadn't tested the code in the lesson to see if it would actually run. |
|
@avadean Do you think this is ready to merge? |
|
Yes looks great to me! @LiamPattinson |
Auto-generated via `{sandpaper}`
Source : fe7b28e
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-02-16 17:42:00 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : de7a5aa
Branch : main
Author : Liam Pattinson <LiamPattinson@users.noreply.github.com>
Time : 2026-02-16 17:40:31 +0000
Message : Merge pull request #12 from ResearchCodingClub/floating_point
Add chapter on floating point data
Resolves #7
Resolves #9
Changes data structures chapter to one about handling floating point numbers.
math.isclose, then goes straight to NumPy routines (skipsnp.isclosefor simplicity)Additionally includes some edits to the setup doc.